Module displayed name different from module properties

I notice that when a module is copied and the name of the copy is then changed that sometimes the module properties are not updated with the new name that is displayed in the GUI.

This does not always happen, and I have so far been unable to nail the cause.

I would like to know if anyone else has seen this behaviour.

The code below will highlight differences.
 

ModuleProperties mp 
ModuleVersion mv 
Item selectedItem
string displayedName = ""
string propName = ""
 
for selectedItem in current Folder do
{
    if (type(selectedItem) == "Formal")
        {
                mv = moduleVersion(module(fullName(selectedItem))) 
                getProperties (mv, mp) 
        
                
                displayName = name(selectedItem) ""
                propName = mp."Name" ""
 
                if (propName != displayName)
                {
                        //print "FullName: " fullName(selectedItem) "\n"
                        print "Displayed Name: "displayName "\n"
                        print "Name in Properties: " propName "\n\n"
                }
        }
}

 


Tony Goodman, www.smartdxl.com

 


Tony_Goodman - Wed Sep 19 10:15:06 EDT 2012

Re: Module displayed name different from module properties
llandale - Wed Sep 19 15:29:48 EDT 2012

Where have you been?

I see AutoDeclare is on since you declare "displayedName" but use "displayName". I tweaked your code a little. Using v9306.

I see this behavior when you rename a module with Properties, but see nothing to relate it to copying. Get the same results when I open a new instance of DOORS. Same results when I open Edit the offending module and save and close it. Same result when I search for items in the Project. I see I found an very old renamed module and it has the same issue. The module properties seems to remember the OLD name.

Seems like "ModuleProperties" isn't working quite right and I find that very disturbing.

You want to submit a PMR? They have so far rejected all but one of mine (such as the one where I could not create a project because of a bad character in the name, but the isValidName said it was OK).

-Louie

ModuleProperties mp 
ModuleVersion mv 
Item selectedItem
string displayName = ""
string propName = ""
bool    YesOpen = confirm("Open modules?")
for selectedItem in current Folder do
{
        if (type(selectedItem) == "Formal")
        {
                mv = moduleVersion(module(fullName(selectedItem))) 
                getProperties (mv, mp) 
        
                
                displayName = name(selectedItem) ""
                propName = mp."Name"
//              propName = name(mp)
 
                if (propName != displayName)
                {
                        //print "FullName: " fullName(selectedItem) "\n"
                        print "Difference. \tDisplay/Property name  ["displayName "]\t[" propName "]\n"
                }
                else    print "Same:       \t[" propName "]\n"
                if (YesOpen)
                {  Module m = read(propName, false, true)
                   if (null m) print "\tCannot open [" propName "]\n"
                }
        }
}

Re: Module displayed name different from module properties
Mathias Mamsch - Thu Sep 20 04:34:04 EDT 2012

llandale - Wed Sep 19 15:29:48 EDT 2012

Where have you been?

I see AutoDeclare is on since you declare "displayedName" but use "displayName". I tweaked your code a little. Using v9306.

I see this behavior when you rename a module with Properties, but see nothing to relate it to copying. Get the same results when I open a new instance of DOORS. Same results when I open Edit the offending module and save and close it. Same result when I search for items in the Project. I see I found an very old renamed module and it has the same issue. The module properties seems to remember the OLD name.

Seems like "ModuleProperties" isn't working quite right and I find that very disturbing.

You want to submit a PMR? They have so far rejected all but one of mine (such as the one where I could not create a project because of a bad character in the name, but the isValidName said it was OK).

-Louie

ModuleProperties mp 
ModuleVersion mv 
Item selectedItem
string displayName = ""
string propName = ""
bool    YesOpen = confirm("Open modules?")
for selectedItem in current Folder do
{
        if (type(selectedItem) == "Formal")
        {
                mv = moduleVersion(module(fullName(selectedItem))) 
                getProperties (mv, mp) 
        
                
                displayName = name(selectedItem) ""
                propName = mp."Name"
//              propName = name(mp)
 
                if (propName != displayName)
                {
                        //print "FullName: " fullName(selectedItem) "\n"
                        print "Difference. \tDisplay/Property name  ["displayName "]\t[" propName "]\n"
                }
                else    print "Same:       \t[" propName "]\n"
                if (YesOpen)
                {  Module m = read(propName, false, true)
                   if (null m) print "\tCannot open [" propName "]\n"
                }
        }
}

I have a guess what happens, although I cannot nail the cause. DOORS has the module name and description stored redundant. One time in the folder index file (module.ixc) (which is cleartext by the way) and one time as an attribute value in the treedata.dtc. The ModuleProperties will access the module attribute value. I guess the 'name' perm and other perms that access the item hierarchy seem to access to folder index file only.

So what is likely to happen here, is that somehow the module index file and the module attributes go out of sync regarding the name. I cannot tell however how this is happening. Can you check if name(Module) and name(Item) yield different results? Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Module displayed name different from module properties
Tony_Goodman - Fri Sep 21 04:38:29 EDT 2012

Mathias Mamsch - Thu Sep 20 04:34:04 EDT 2012
I have a guess what happens, although I cannot nail the cause. DOORS has the module name and description stored redundant. One time in the folder index file (module.ixc) (which is cleartext by the way) and one time as an attribute value in the treedata.dtc. The ModuleProperties will access the module attribute value. I guess the 'name' perm and other perms that access the item hierarchy seem to access to folder index file only.

So what is likely to happen here, is that somehow the module index file and the module attributes go out of sync regarding the name. I cannot tell however how this is happening. Can you check if name(Module) and name(Item) yield different results? Regards, Mathias


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

I checked this properly, and as Louie said this is nothing to do with copying.

The module name property remains at the original name after it is renamed.

I have raised a bug report with our IT guys who will forward it on to IBM.

Tony Goodman, www.smartdxl.com

Re: Module displayed name different from module properties
Tony_Goodman - Thu Oct 04 04:51:48 EDT 2012

Tony_Goodman - Fri Sep 21 04:38:29 EDT 2012
I checked this properly, and as Louie said this is nothing to do with copying.

The module name property remains at the original name after it is renamed.

I have raised a bug report with our IT guys who will forward it on to IBM.

Tony Goodman, www.smartdxl.com

IBM have accepted this as a defect.
PMR tracking ID APAR # PM73846

Tony Goodman, www.smartdxl.com

Re: Module displayed name different from module properties
MikkaXXX - Wed Jun 19 07:28:00 EDT 2013

Tony_Goodman - Thu Oct 04 04:51:48 EDT 2012
IBM have accepted this as a defect.
PMR tracking ID APAR # PM73846

Tony Goodman, www.smartdxl.com

Hello Tony,

Where can I find further information about this issue?

I have the same problem and I'm interested in a fix.

Regards

Mikka

Re: Module displayed name different from module properties
GregM_dxler - Wed Jun 19 10:14:31 EDT 2013

Tony_Goodman - Thu Oct 04 04:51:48 EDT 2012
IBM have accepted this as a defect.
PMR tracking ID APAR # PM73846

Tony Goodman, www.smartdxl.com

Hi Tony and all,

Thanks for posting this issue.  However, I'm a little confused as to detecting this issue and maybe doing a workaround.  I run the script and it highlights a module that has a different display name from the property name.  However, when I look at the Module Properties of the module, the Name field has the same name as the displayed name.  I looked at the module properties from both the explorer window and from inside the module (File->Module Properties...).

Where is this property name listed at and how can I change it, short of generating a script to do it?

Thanks,

Greg